Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server

Running the Progress-to-MSS utility

The Progress-to-MSS utility runs in Windows with a DataServer accessing MS SQL Server through an ODBC driver.

You can run the utility interactively from Windows or Unix, or in batch mode.

Running the Progress-to-MSS utility interactively

To run the Progress-to-MSS utility interactively:
  1. Create a target MS SQL Server. You must use an empty target data source when you run the Progress-to-MSS utility.

  2. Configure your ODBC driver to connect to your new target data source.

  3. Start the OpenEdge client and connect to the OpenEdge database that you want to migrate to the target data source.

    4. Note: For a DBE (double-byte enabled) DataServer application, you must specify the Internal Code Page (-cpinternal) and Stream Code Page (-cpstream) parameters when you start the OpenEdge client. The values that you specify for these parameters must match the code page that the target data source uses.

  4. From the Data Administration tool, choose DataServer MS SQL Server Utilities Schema Migration Tools Progress DB to MS SQL Server. The following screen appears:

    5. It prompts you for the information described in Table 7–5.

    Table 7–5: Progress-to-MSS utility
    Interface element
    Description
    Original PROGRESS Database
    Accept the default value of sports, which is displayed.
    Connect parameters for PROGRESS
    Accept the default value, which specifies the current working database.
    Name of Schema holder Database
    Type myholder.
    Logical Database Name
    Type the name that OpenEdge will use to identify the MS SQL Server database.
    ODBC Data Source Name
    Type mysport, which is the name you used when registering the data source.
    Username
    Type the user ID for MS SQL Server.
    User’s Password
    Type the password of the user.
    Connect parameters
    See Chapter 6, "Connecting the DataServer," for connection parameters.
    MaximumVarchar Length
    Enter the maximum size of the VARCHAR field. Any size greater will be text. Max size is 8000.
    Codepage
    Accept the default code page.
    Collation
    Accept the default.
    Insensitive
    Accept the default.
    Create RECID Field
    If this parameter is available for your data source type, check this toggle box to obtain the Extended 4GL capability.
    Load SQL
    Leave this box checked to have the generated SQL script loaded into the data source.
    Move Data
    Check this toggle box to dump and load data from OpenEdge to MS SQL Server.
    Create Shadow Columns
    MS SQL Server is case insensitive by default and this box is unmodifiable. When SQL Server is configured with a case sensitive code page, this box is available for selection. Selecting it provides case insensitivity compatible with the behavior of an OpenEdge database.
    Include Defaults
    Check if you want the OpenEdge initial value used as the default in the SQL script.
    For fields width use:
    When pushing fields to a foreign data source, you can select one of two primary field format options:
    • Width—Uses the value of the _width field in the _field record.
    • 4GL Format—Compiles with the current default width specified. (default)
    If you select the 4GL Format option, you have an additional setting to define:
    • Expand x(8) to 30—This setting is on by default to indicate that the format for the character fields defined as x(8) will be created as 30 characters.

    Note: You cannot use the Expand x(8) to 30 setting with the Width option.

To perform a complete migration of your OpenEdge database to a target data source, you must enter information in all appropriate fields and check all appropriate toggle boxes.

The utility creates a schema holder, updates the empty target data source that you created to contain the objects stored in your OpenEdge database, and creates a startup procedure that you can use to connect your schema holder. The startup procedure derives its name from the logical name for your target database. For example, if you specified “sports” as the logical data source name, the utility creates the csports.p startup procedure.

Running the Progress-to-MSS utility in batch mode

To run the Progress-to-MSS utility in batch mode:
  1. Create a target MS SQL Server database. You must use an empty target data source when you run the Progress-to-MSS utility.

  2. Configure your ODBC driver to connect to your new target data source.

  3. On your client machine, pass parameters to the utility by setting the environment variables listed in Table 7–6.
    Table 7–6: Progress-to-MSS utility batch parameters
    Environment variable

    Description
    PRODBNAME
    Specifies the source OpenEdge database name.
    PROCONPARMS
    Specifies parameters for the connection to the source OpenEdge database.
    SHDBNAME
    Specifies the new schema-holder name.
    MSSDBNAME
    Specify ODBC data source name.
    MSSPDBNAME
    Specify logical database name.
    MSSUSERNAME
    Specifies the user name for the target data source.
    MSSPASSWORD
    Specifies the password of the user for the target data source.
    MSSCONPARMS
    Specifies additional connection parameters for the schema holder.
    MSSCODEPAGE
    Specifies the OpenEdge name for the code page that the ODBC data source uses. By default, the code page for a schema holder is ibm850. You can leave this field blank and use the Change DataServer Schema Code Page utility to add the code page information for the schema holder later.
    MSSCOLLNAME
    Collation name.
    MSSCASESEN
    Yes or No for Code Page case sensitive.
    COMPATIBLE
    Create arrays and RECID.
    VARLENGTH
    Total number of characters a VARCHAR can have. Any field whose format is greater that will be defined as a text field. Maximum is 8000.
    SQLWIDTH
    If present, use the OpenEdge file _WIDTH field size instead of calculating length by using the display format.
    LOADSQL
    Allows you to specify whether you want the utility to create the schema in your empty MS SQL Server database. Specify YES to enable this behavior.
    MOVEDATA
    Allows you to specify whether to populate the database. Specify YES to dump and load data or NO to not populate the database. For example, you might specify NO if your database is large, and you want to dump and load data at a more convenient time. The default is NO.

  4. Enter the following commands to set and export environment variables at the system prompt:

    5. PRODBNAME=db-name; export PRODBNAME
PROCONPARMS="-1 -i"
SHDBNAME=schema-holder-name; export SHDBNAME
.
.
.
pro -b -p prodict/mss/protomss.p

  5. Run protomss.p.

Copyright © 2005 Progress Software Corporation
 www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095